Configurability

OpsCenter Configurability

Each Organization is different. It has unique terminology, processes and organization. OpsCenter has been designed to be tailored to match the unique aspects of each organization. This allows the software to change to match the organization, not the other way around. OpsCenter's configurability allows experts within your organization to configure the system to make it easier for the less experienced users. 

OpsCenter adapts to Your Terminology

The terminology used in OpsCenter is easily configured by a non-technical person. It does not matter to OpsCenter if you chose to call the actions taking place to response to an Incident a 'Mission', an 'Assigned Action', a 'Tasking' or something else. A non-technical person can decide what terminology to use throughout the system. An example of the OpsCenter Terminology screen is show above.

OpsCenter adapting to Your Content

The fields in OpsCenter can be turned off and on by a non-technical person. This allows OpsCenter to capture all the information, and only the information, that is important to your organization. For example, if your organization does not use Operational Periods as a part of your response process then those fields would be turned off to avoid confusion for your users. 

OpsCenter adapts to Your Organizational Structure

In addition to modifying existing roles and creating new ones, you can decide what each role has access to in the system and the type of access. The OpsCenter Roles Administration Screen is show above.

Adapting to Your Language

Since all text in OpsCenter, including buttons, can be edited externally, localization requires a minimum of effort.

Adapting to Your Look & Feel

Colors and graphics can be readily changed to match your logo or other appearance requirements.

Configuration, Customization, and Engineering

OpsCenter is highly configurable, and many changes can be made by trained users, requiring no technical assistance. When making changes to the system, it is important to keep in mind the difference between configuration, customization, and engineering, and the impact each has on the implementation:

• Configuration can be performed by non-technical users, has the least short-term cost, and is automatically carried forward across upgrades so it has no long-term cost.
• Customization requires technical personnel to perform but does not carry forward across upgrades, is more difficult and time consuming, and is more expensive, both short-and-long-term.
• Engineering must be performed by Alert Technologies, takes the longest to deliver, and comes in the form of updates to OpsCenter itself. Since engineering changes become a permanent part of OpsCenter, there is no long-term cost.  This type of change is automatically carried forward across upgrades.